home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
SGI Desktop Special Edition 1.1
/
SGI Desktop Special Edition 1.1.iso
/
relnotes
/
patchSG0000670
/
ch1.z
/
ch1
Wrap
Text File
|
1995-11-13
|
8KB
|
265 lines
- 1 -
1. _P_a_t_c_h__S_G_0_0_0_0_6_7_0__R_e_l_e_a_s_e__N_o_t_e
This release note describes patch SG0000670 to IRIX 5.3.
1.1 _S_u_p_p_o_r_t_e_d__H_a_r_d_w_a_r_e__P_l_a_t_f_o_r_m_s
This patch contains bug fixes for all platforms.
1.2 _S_u_p_p_o_r_t_e_d__S_o_f_t_w_a_r_e__P_l_a_t_f_o_r_m_s
This patch contains bug fixes for IRIX 5.3 and IRIX 5.3 with
XFS. The software cannot be installed on other
configurations.
1.3 _B_u_g_s__F_i_x_e_d__b_y__P_a_t_c_h__S_G_0_0_0_0_6_7_0
This patch contains fixes for the following bugs in IRIX 5.3
and IRIX 5.3 with XFS. Bug numbers from Silicon Graphics
bug tracking system are included for reference.
+o The IP multicast support did not prune multicasts when
they were not needed (bug 255570).
+o IP multicast multicast routers with more than two
interfaces decremented the time-to-live field too
often, and could corrupt the IP header checksum (bug
249138).
+o When TCP connections are being created and destroyed at
high rate, a multiprocessor system may panic with a
segmentation violation (bug 248734). This fix avoids
the race between accept() and tcp_drop() on
multiprocessor machine.
+o When TCP connections are being created at a high rate,
a system panic may occur with message "soaccept
!NOFDREF" (bug 249206). This fix avoids the race
between accept() and tcp_drop().
+o When TCP connections are being created at a high rate,
connections may time out even though the server is
largely idle, due to the backlog limit on the server's
initial connection socket being limited to a small
value (bug 245976). This change allows the maximum
backlog value to be reconfigured, by modifying the
variable somaxconn in /var/sysgen/master.d/bsd.
+o When remote TCP clients disappear forever (where the
client systems do not respond to pings), with
connections open and data queued for output, after the
local server has closed the connection, but before all
- 2 -
the data has been delivered and acknowledged, the TCP
socket is left in the kernel indefinitely, even if the
server set the SO_KEEPALIVE option (bug 248935). This
eventually uses up all available network buffer space.
This change adds a new kernel variable,
tcp_keep_timer_in_close, located in
/var/sysgen/master.d/bsd. This variable may be set to
a non-zero value, to permit SO_KEEPALIVE timeouts to
act on such sockets. The variables tcp_keepidle (the
basic SO_KEEPALIVE timeout period) and tcp_keepintvl
(the SO_KEEPALIVE probe interval) are now located in
/var/sysgen/master.d/bsd as well, to simplify modifying
them. On heavily used TCP servers, it may be useful to
reduce tcp_keepidle from the default (2 hours) to
something less (perhaps 15 minutes).
+o The automount daemon may hang for several minutes at a
time or the sendto() system call may churn up lots of
system cpu for a non-bound UDP socket for MP systems.
Incoming UDP packets for a specific socket may be
discarded if an application is currently executing a
sendto() system call on the UDP socket. One particular
symptom is the local automount deamon not responding to
a request (mount or symlink LOOKUP) for 30 seconds or
longer while the local nfs kernel client code (/hosts/
mount) times out and retries the request. The dropped
UDP packets show up in the udp section of "netstat -s"
output with the label "XXX datagrams dropped due to no
socket". Other programs which use UDP extensively may
encounter this problem of incoming packets dropped
while the program is executing a sendto() syscall. The
problem is due to the way the sendto() system call is
implemented over UDP in 5.3 . Each sendto() causes a
connect/udp_output/disconnect to be done on the socket
which may (1) encounter high lock contention and (2)
will discard packets received for this socket which
arrive during the sendto(). The fix is to properly
multithread sendto() for UDP to allow concurrent
transmit and receive. Bugs 252553 and 258545.
+o IRIX did not include the base support necessary for
firewall to firewall encryption feature of the Gauntlet
firewall product.
1.4 _S_u_b_s_y_s_t_e_m_s__I_n_c_l_u_d_e_d__i_n__P_a_t_c_h__S_G_0_0_0_0_6_7_0
This patch release includes these subsystems:
+o patchSG0000670.eoe1_sw.svr4net
- 3 -
+o patchSG0000670.eoe1_sw.unix
+o patchSG0000670.eoe2_sw.ipgate
+o patchSG0000670.eoe2_sw.tcp
1.5 _I_n_s_t_a_l_l_a_t_i_o_n__I_n_s_t_r_u_c_t_i_o_n_s
Because you want to install patches for only the problems
you have encountered, patch software is not installed by
default. After reading the descriptions of the bugs fixed in
this patch, determine the patches that meet your specific
needs.
Patch software is installed like any other Silicon Graphics
software product. Follow the instructions in your _I_R_I_S
_S_o_f_t_w_a_r_e _I_n_s_t_a_l_l_a_t_i_o_n _G_u_i_d_e to bring up the miniroot form of
the software installation tools.
Follow these steps to select a patch for installation:
1. At the Inst>prompt, type
iiiinnnnssssttttaaaallllllll ppppaaaattttcccchhhhSSSSGGGG_x_x_x_x_x_x_x
where _x_x_x_x_x_x_x is the patch number.
2. Select the desired patches for installation.
3. Initiate the installation sequence. Type
IIIInnnnsssstttt>>>> ggggoooo
4. You may find that two patches have been marked as
incompatible. If this occurs, you must deselect one
of the patches.
IIIInnnnsssstttt>>>> kkkkeeeeeeeepppp ppppaaaattttcccchhhhSSSSGGGG_x_x_x_x_x_x_x
where _x_x_x_x_x_x_x is the patch number.
5. After completing the installation process, exit the
_i_n_s_t program by typing
IIIInnnnsssstttt>>>> qqqquuuuiiiitttt
To remove a patch, use the _v_e_r_s_i_o_n_s _r_e_m_o_v_e command as you
would for any other software subsystem. The removal process
reinstates the original version of software unless you have
- 4 -
specifically removed the patch history from your system.
vvvveeeerrrrssssiiiioooonnnnssss rrrreeeemmmmoooovvvveeee ppppaaaattttcccchhhhSSSSGGGG_x_x_x_x_x_x_x
where _x_x_x_x_x_x_x is the patch number.
To keep a patch but increase your disk space, use the
_v_e_r_s_i_o_n_s _r_e_m_o_v_e_h_i_s_t command to remove the patch history.
vvvveeeerrrrssssiiiioooonnnnssss rrrreeeemmmmoooovvvveeeehhhhiiiisssstttt ppppaaaattttcccchhhhSSSSGGGG_x_x_x_x_x_x_x
where _x_x_x_x_x_x_x is the patch number.